Curse

djwheat · May 10, 2005, 04:18 AM // 04:18

I recently posted on these forums in regard to a "crashing to desktop with an ArenaNet Error log" problem. I was constantly sending the logs to ArenaNet, with as much information as possible... however, I'm curious as to whether or not anyone else has seen or heard of this problem.

In my prior GW Tech Support issues, I had this error which referenced DxTex.CPP or DxShad.CPP. All the while I assumed this error HAD to do with DirectX. I happened to have a GeForceFX 5900 at work so I replaced that card for the ATI 9200 I had in my box. Reformatted just to make sure.

Installed the game (this time from the CD) and played for a good 10 hours with no problems. Suddenly... game crashes again. I thought I was scott free, unfortunately this was not the case. I played through it tho, as these errors were happening every 3 to 4 hours. I could manage that, although it was upsetting to have to restart a mission half way through it (I also feel bad for my Guild!!!).

Sunday was a different story as I was unable to get any play time in. So around comes Monday (today)... I get home jump on, and within 1 hour of gameplay I've had THREE crashes. One of them a complete computer reboot, while the other two referenced GrModel.CPP.

Again I sent the report, however, I fail to believe that there isn't someone else out there who has experienced something like this. It's gotten now to the point where I just cannot play... everytime I try to make some progress with a group and I get reset or crash, I'm forced to restart or am left behind.

I beg that if anyone has experienced this or may know what this reference please assist.

PS Before I finished this I checked my Guild Wars directory for error logs. Here is what I had... you'll notice the DxShad/DxTex error I had before, and then the newest one GrModel.

#1:
*--> Crash <--*
Assertion: Invalid bits in TSS mask
DxShad.cpp(415)
App: Gw.exe
ProgramId: 1
Build: 10641
When: 5/7/2005 15:36:23
Flags: 0

#2:
*--> Crash <--*
Assertion:
GrModel.cpp(1724)
App: Gw.exe
ProgramId: 1
Build: 10641
When: 5/9/2005 20:04:37
Flags: 0

*--> LogQueue <--*
(2) Gadget launch animation lacks execute trigger
(2) Gadget launch animation lacks execute trigger
(2) Gadget launch animation lacks execute trigger
(2) Gadget launch animation lacks execute trigger
(1) ProcessBlt(): No direct blitter for conversion from DXT1 to DXT5 (preserve rgb)

*--> DirectX Device Info <--*
VendorId = 0x10de
DeviceId = 0x0332
Version = 6.14.0010.7189
Description = NVIDIA GeForce FX 5900XT
Compat = 0x00800000
VidMem = 128 MB

ZennZero · May 10, 2005, 12:43 PM // 12:43

The fact that you are having these errors after a complete reformat and video card swap (and resulting video drivers) makes me think you have some hardware instability. This could be the physical hardware itself, or the drivers you are using for a given component (you have already eliminated the video card as a problem). The strange thing is that your errors seem to be all over the place.... First a DX shader issue then what appears to be a scripting error and/or texture problem? I would systematically test my hardware trying to find the failure point (new drivers, swap hardware, rinse and repeat). Don't forget to check your networking device too -- a few key dropped packets could produce the kind of inconsistent results you see here...

djwheat · May 10, 2005, 02:59 PM // 14:59

I've already begun testing various components of my machine. For example, last evening I ran memtest89. Had 12 cycles with no failures. Today I will run Everest.

Also just out of curiosity, how could the network device cause these errors? The reason I ask in more detail, is because there were a few crashes which seemed to be a result of X-Fire. I don't know if that was the case 100%, but it seemed strange. Of course afterwards I played many hours without X-Fire only to experience the same problems.

ZennZero · May 10, 2005, 03:33 PM // 15:33

The simplified answer is that it has to do with Guild War's fundamental (and rather unusual) architecture. In order to prevent cheating ALL game mechanics are handled server side. When you do something in GW, all you are transmitting are click coordinates and button presses. Actually deciding what function results is done on their end. So, when you get an error like this:

(2) Gadget launch animation lacks execute trigger

What immediately comes to mind is that (for some reason) your client is not getting the action triggers it is expecting from the server. This could be a result of packet loss, extreme lag, etc. I am just making educated guesses, but it's worth investigating.

djwheat · May 10, 2005, 05:33 PM // 17:33

Interesting. I did replace my NIC drivers (I was using default WinXP 3COM drivers). I know that it cannot be anything with my router or cable modem because my wife is playing right beside me and experiences ZERO issues with her game.

In addition, after running for 2 years with no problems overclocked, I have turned it off, will run it for the day, and try a GW session with no overclocking this evening.

Kerrick · May 11, 2005, 01:12 AM // 01:12

I feel the same way, mine keeps crashin and i dunno what to do about it....

Ive had these errors
*--> Crash <--*
Exception: c0000005
Memory at address 029268c8 could not be read
App: GW.EXE
ProgramId: 1
Build: 10631
When: 5/3/2005 12:08:10
Flags: 0

*--> LogQueue <--*
(1) Unexpected Win32 error [0x57]

*--> DirectX Device Info <--*
VendorId = 0x1002
DeviceId = 0x514c
Version = 4.14.0001.0247
Description = RADEON 8500 SERIES
Compat = 0x00010000
VidMem = 127 MB

*--> Crash <--*
Assertion:
GrModel.cpp(1356)
App: GW.EXE
ProgramId: 1
Build: 10641
When: 5/6/2005 02:40:42
Flags: 0

*--> Crash <--*
Assertion:
P:\Code\Base\rtl/IdMgr.h(72)
App: GW.EXE
ProgramId: 1
Build: 10641
When: 5/6/2005 02:42:24
Flags: 0

*--> Crash <--*
Assertion:
TrnQueryLine.cpp(156)
App: GW.EXE
ProgramId: 1
Build: 10641
When: 5/6/2005 02:45:26
Flags: 0

*--> Crash <--*
Exception: c0000005
Memory at address ffffffff could not be read
App: GW.EXE
ProgramId: 1
Build: 10641
When: 5/8/2005 21:46:13
Flags: 0

*--> Crash <--*
Assertion:
DxShad.cpp(138)
App: GW.EXE
ProgramId: 1
Build: 10641
When: 5/8/2005 23:52:29
Flags: 0

the list goes on lol, im gettin very tired of tryin to play this game, its great, but i think my comp is messed up lol

djwheat · May 11, 2005, 01:23 AM // 01:23

Do you happen to overclock? And have you tested your memory? You seem to have the exact same crash problems as I do.

Kerrick · May 12, 2005, 03:03 AM // 03:03

Yes i do overclock, im using a 1 ghz AMD, and i tested my ram last night, i believe its my PSU is dyin so im getting a new one

EnDinG · May 12, 2005, 01:18 PM // 13:18

Guild Wars is not an overclocked anything friendly game. I'd have to suggest turning it off and hoping for the best.

*--> Crash <--*
Exception: c0000005
Memory at address ******** could not be read
App: Gw.exe
ProgramId: 1
Build: 10641
When: */**/**** **:**:**
Flags: 0

This is a very common error and I've been reading around the threads with this error to see what might be causing it. A lot of the time it has to do with memory and loading graphics.

I'd have to suggest turning some of the detail down and playing. Last night I did that just on a whim (terrian detail) and managed to keep my connection all night without my wonderful Err=7 problem.

Farox · May 17, 2005, 04:20 AM // 04:20

I'll reply to this thread as it deals with what I have issues.

I have latest Chipset Drivers, and BIOS Which finaly solved this dandy:

Assertion:
P:\Code\Base\rtl/Array.h(559)
App: Gw.exe
ProgramId: 1
Build: 9334
When: 3/19/2005 08:35:57
Flags: 0

and this one:

Exception: c0000005
Memory at address 0000010c could not be read
App: Gw.exe
ProgramId: 1
Build: 10231
When: 4/17/2005 18:41:45
Flags: 0

But nothing I did til now could help with the infamous:

Assertion: !FAILED(result), result = 0x8876086c
DxShad.cpp(1603) <--- Im led to believe this is a Shader issue
App: Gw.exe
ProgramId: 1
Build: 10782
When: 5/15/2005 11:51:38
Flags: 0

I have a 9600 256MB card, FYI.

I tried 3 dif ATI drivers including the latest Omega Drivers, all with the same result: Crahing at random intervals at least 4 to 5 times per session. I downstepped my AGP to 4X from 8X, disabled Fastwrites... the list goes on. I've sent over 70 error logs to Arena Net.

What I have found to work... 8 hours so far in-game, I've just let it run... (knock on wood) has been to add the -NoShaders command to my Guild Wars shortcut. End result should look like this:

"X:\Program Files\Guild Wars\Gw.exe" -NoShaders

Where X = drive you have GW installed.

Now, without shaders the game looks a little dif. No "auras" on bosses (Which makes them a little dificult to tell apart from others), and capes are a little more in contrast and lose their sheen. Apart from that the game looks just fine. On the upside, I have yet to crash... *crosses fingers*

Hopefully those with similar DxShad.cpp errors can find the -NoShaders command usefull and perhaps feel confident in trying HoH or some of the later missions without fear of crashing midway thru. How I've made it to Ascension with all these crashes amazes my Guildmates, and hopfully I can once again start to grow my hair back from where I have yanked it out in frustration.

Cheers.

EnDinG · May 17, 2005, 01:02 PM // 13:02

After reading some of the problems with these errors caused by graphics, I'd have to say a lot of it is just a bad file.

If people continue with the errors even after a fresh install / format of GW and XP, check your CD and see if there are any lines or dust on it.

If you download the game, there is always a chance your connection will cough and miss a part of the game / file. I would suggest trying a fresh download if your one of the people who have done that and are getting errors.

By rights, there should be no reason to shut off parts of the game. Problem files can be fixed.

Farox · May 17, 2005, 04:43 PM // 16:43

Yeah, reinstalled 5 times, even tried the DL from the GW site and my Beta Client... still same issues. I never had these issues on my Old Box during Beta events. Only since I have changed Mobo/Cpu/Memory/Vid Card have these issues popped up.

WoW would drop me with the memory assertion error, very similar to the GW I used to get. Happened to be that my Mobo didnt like the DDR 400 memory and needed a BIOS update to fix the issues that particular Board had: ECS PT800. Now I do not get the memory assertion error, not once since update, in either game.

The fact that having to update my BIOS to fix a memory assertion error, led me to believe these errors are not whole or in part due to a bad install. But probably based on certain Hardware I have.

Now the ATI 9600 card I have is frankly outdated and a very poor purchase on my part, and it seems that this card is the culprit in the DxShad.cpp issue I have if I do not turn of Shaders via command line. Im going to get rid of it ASAP and go with nVidia like I always have in the past.

But, until I hear something from Arena Net telling me it was their fault and not my hardware etc. I have to turn off shaders to play this game til it is sorted out somehow.

This workaround works for me, no crashes in 2 days. I figured I'd put it out there seeing as I wasnt the only one on the recieving end of the crash. At least I can play the game now.

Cheers

EnDinG · May 17, 2005, 07:55 PM // 19:55

Useful posts in this thread, going to add it to our collection for the index. Thanks guys.

Serafita Kayin · May 17, 2005, 09:17 PM // 21:17

And for us tweakers, I think a reward of how to make GW overclock friendly is in order...